Network based archiving of user-specific information in a communication system

ABSTRACT

User-specific information (e.g., call log information, contact information, etc.) normally stored within a mobile user device associated with a user is also maintained at one or more network storage locations within a communication system. The information may thereafter be easily transferred from the network storage location(s) to a new user device associated with the user.

BACKGROUND OF THE INVENTION

[0001] A mobile user device, such as a cellular telephone or a pager, isoften capable of storing information that is specific to the userassociated with the device. This may include, for example, informationrelating to personal contacts of the user (i.e., contact information)and information relating to calls that the user recently participated in(i.e., call log information). Having such information within the userdevice can provide many conveniences to the user. For example, if theuser has to contact a business associate from a remote location and doesnot remember the party's telephone number, the number can be easilyretrieved from a memory within the user device (assuming the user haspreviously programmed the number into the device). The user device mayalso be capable of automatically dialing the party's telephone numberfor the user. If the user wants to contact a party with whom he/she justspoke the previous day, the telephone number of the party may be easilyretrieved from the call log in the user device. Automatic dialing ofcall log listed numbers may also be provided. When a user purchases anew user device (e.g., when an old device is lost, stolen, damaged, oroutdated), the new device will not have the user-specific informationstored therein. Thus, if the user wants to have access to his/hercontact information, the user will typically have to remember andmanually enter the contact information in the new user device. The calllog information will usually be irretrievably lost.

BRIEF DESCRIPTION OF THE DRAWINGS

[0002]FIG. 1 is a block diagram illustrating a communication system inaccordance with an embodiment of the present invention;

[0003]FIG. 2 is a block diagram illustrating a user device in accordancewith an embodiment of the present invention;

[0004]FIG. 3 is a block diagram illustrating a network server andassociated memory in accordance with an embodiment of the presentinvention;

[0005]FIG. 4 is a flowchart illustrating a method for processing callswithin a communication system in accordance with an embodiment of thepresent invention;

[0006]FIG. 5 is a flowchart illustrating a method for performing addressbook auto-synchronization for a mobile user device in a communicationsystem in accordance with an embodiment of the present invention; and

[0007]FIG. 6 is a flowchart illustrating a method for use in supportingan address book storage and retrieval service within a communicationsystem in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION

[0008] In the following detailed description, reference is made to theaccompanying drawings that show, by way of illustration, specificembodiments in which the invention may be practiced. These embodimentsare described in sufficient detail to enable those skilled in the art topractice the invention. It is to be understood that the variousembodiments of the invention, although different, are not necessarilymutually exclusive. For example, a particular feature, structure, orcharacteristic described herein in connection with one embodiment may beimplemented within other embodiments without departing from the spiritand scope of the invention. In addition, it is to be understood that thelocation or arrangement of individual elements within each disclosedembodiment may be modified without departing from the spirit and scopeof the invention. The following detailed description is, therefore, notto be taken in a limiting sense, and the scope of the present inventionis defined only by the appended claims, appropriately interpreted, alongwith the full range of equivalents to which the claims are entitled. Inthe drawings, like numerals refer to the same or similar functionalitythroughout the several views.

[0009] The present invention relates to techniques and structures foruse within a communication system to provide additional,convenience-enhancing services to mobile users. User-specificinformation (e.g., call log information and/or contact information)normally stored within a mobile user device associated with a user isalso maintained at one or more network storage locations within thesystem. Thus, should the user's communication device be lost, damaged,or stolen, or should the user simply desire to trade up to a new devicemodel, the user-specific information may be easily downloaded to a newuser device from the network storage location(s). In this manner, theprocess of acquiring and configuring a new user device may be madesimpler and more convenient for a user. In at least one embodiment, themaintenance of user-specific information within the network is offeredto users on a subscription basis.

[0010]FIG. 1 is a block diagram illustrating a communication system 10in accordance with an embodiment of the present invention. Thecommunication system 10 may be part of a larger (e.g., cellular-based orsatellite-based) communication system for providing communicationservices to mobile users. As illustrated, the communication system 10includes: a base station 12, a network 14, a server 16, a memory 18, anda user device 20. The user device 20 may comprise any form of portablecommunication device having wireless transceiver functionalityincluding, for example, a mobile telephone (e.g., a cellular telephone,a handheld satellite communicator, etc.), a personal digital assistant,a pager, and others. The base station 12 provides wireless access to thenetwork 14 for the user device 20. The base station 12 may also provideaccess to the network 14 for one or more other user devices (not shown)within the coverage region of the base station 12. One or more otherbase stations may also be coupled to the network 14 to provide wirelessaccess thereto for corresponding users. In this manner, communicationconnections may be established and maintained between mobile userswithin the communication system 10. The network 14 may also be coupledto one or more external networks (e.g., the public switched telephonenetwork, the Internet, etc.) to allow communication connections to beestablished and maintained between a mobile user in the communicationsystem 10 and one or more entities outside of the communication system10. It should be appreciated that the communication system 10 of FIG. 1is merely exemplary of a system in which the inventive principles may bepracticed. Many alternative system architectures may also be used.

[0011] The server 16 is coupled to the network 14 for providing one ormore network functions and/or user services within the communicationsystem 10. The server 16 will typically include one or more digitalprocessing devices (e.g., a general purpose microprocessor, a digitalsignal processor (DSP), a reduced instruction set computer (RISC), acomplex instruction set computer (CISC), a field programmable gate array(FPGA), an application specific integrated circuit (ASIC), and/orothers) to facilitate performance of its correspondingfunctions/services. The memory 18 includes a digital storage medium thatmay be used by the server 16 in providing some or all of itscorresponding functions/services. The memory 18 may include any form ofdigital storage device including, for example, a semiconductor memorydevice, a magnetic disk drive, an optical drive, or others, includingcombinations of the above. In at least one embodiment, as shown in FIG.1, the memory 18 is co-located with the server 16. In anotherembodiment, the memory 18 is accessed by the server 16 through thenetwork 14.

[0012]FIG. 2 is a block diagram illustrating a user device 30 inaccordance with an embodiment of the present invention. The user device30 may be used, for example, within the communication system 10 ofFIG. 1. As illustrated, the user device 30 includes: a user interface32, a controller 34, a call log database 36, an address book database38, and an information transfer module 40. The user interface 32provides an interface between the user device 30 and a correspondinguser. As such, the user interface 32 may comprise any of a number ofdifferent input and/or output devices including, for example, a display,a keypad, a speaker, a microphone, control buttons, a keyboard, a mouse,a touch pad, and/or others. The controller 34 controls the operation ofthe user device 30 and may also provide for information processing andtransfer between the user interface 32 and a corresponding wirelesstransceiver. The call log database 36 includes a data storage medium inwhich call log information is stored within the user device 30 for acorresponding user. The call log database 36 may include call-relatedinformation for a predetermined number of previous calls that wereplaced from and/or received through the user device 30. The call logdatabase 36 will typically include the phone numbers of the otherparties involved in the corresponding calls. Party names and/or otherinformation (e.g., length of call, etc.) may also be stored. Thecontroller 34 may control the maintenance of the call log database 36 ora separate control unit can be provided.

[0013] The address book database 38 includes a data storage medium inwhich user-specific contact information is maintained. A user may makeadditions to and/or deletions from the address book database 38 byactivating an appropriate function within the controller 34 and thenmanually entering or deleting contact information using an input device(e.g., a keypad). The address book database 38 will typically includethe telephone numbers and names of contacts specified by the user. Othercontact-related information may also be stored in the address bookdatabase 38.

[0014] The information transfer module 40 is operative for automaticallytransferring contact information from the address book database 38 ofthe user device 30 to a network based storage location within thecommunication system. The information transfers may take place at one ormore predetermined times, which may be specified by the user. In oneapproach, the user specifies a timing criterion for performing transfersat the time the automatic information transfer function is firstactivated within the user device 30. For example, the user may programthe user device 30 to make transfers at periodic intervals (e.g., at10:00 PM every Monday, at 10:00 PM every last day of the month, etc.). Amenu of timing options may be presented to the user to make the entry ofa timing criterion easier. Once appropriately configured, theinformation transfer module 40 will cause the required transfers ofcontact information to be made at the predetermined times. An internalclock may be monitored to determine the present time. The informationtransfer module 40 may transfer all of the contact information from theaddress book database 38 to the corresponding network storage locationeach time a transfer is made or only a portion of the information (e.g.,information that has changed since a previous transfer operation). Inone embodiment, the functions of the information transfer module 40 maybe activated and deactivated by the user using an appropriate inputdevice. The information transfer module 46 may be implemented in avariety of different ways, including both software and hardwareimplementations. In at least one embodiment, for example, theinformation transfer module 40 is implemented in software within thecontroller 34.

[0015] In one approach, the information transfer module 40 will firstcall an appropriate network server in the system, at the predeterminedtime, to request a transfer of contact information to the network. Afteran authentication procedure, the network server may then manage thetransfer and storage of the contact information to the appropriatenetwork storage location. As will be described in greater detail, in atleast one embodiment, a user is required to subscribe to an address bookautosync service (e.g., for a small monthly fee) before automaticinformation transfers will be supported by the network. In addition to,or as an alternative to, automatic transfers of contact information, auser may be able to initiate a transfer of contact information to thenetwork server location manually. For example, a user can manually placea call to a network server requesting a transfer and, after appropriateauthentication, the network server can allow the transfer to proceed.Such capability may also require a subscription to an appropriateservice. As will be appreciated, other techniques for carrying out thetransfer of contact information from a user device to a network storagelocation may alternatively be used.

[0016]FIG. 3 is a block diagram illustrating a network server 42 andassociated memory 46 in accordance with an embodiment of the presentinvention. The server 42 and memory 46 may be used, for example, withinthe communication system 10 of FIG. 1. The server 42 and memory 46 maybe co-located within a communication system or connected through anintervening network (e.g., network 14 of FIG. 1). As illustrated, theserver 42 includes: an authentication module 48, a network billingmanager 50, a call log manager 52, and an address book manager 54. Otherfunctionality may also be provided. It should be appreciated that theindividual blocks illustrated in FIG. 3 (and in other block diagramsdescribed herein) are functional in nature and do not necessarilyrepresent discrete hardware elements. For example, in at least oneembodiment, two or more of the functional blocks (or portions thereof)are implemented in software within a common digital processing device(e.g., a general purpose microprocessor, a digital signal processor(DSP), a reduced instruction set computer (RISC), a complex instructionset computer (CISC), a field programmable gate array (FPGA), anapplication specific integrated circuit (ASIC), and/or others).Individual functions may also be divided among multiple digitalprocessing devices.

[0017] The authentication module 48 is operative for, among otherthings, determining the validity of calls within the system. In atypical scenario, a mobile user is required to have a predeterminedservice agreement in place before outgoing calls can be made from, andincoming calls received by, a corresponding user device. Theauthentication module 48 may check to determine whether such anagreement is in place when an outgoing or incoming call is detected fora particular user device. If it is found that an agreement is in place,the authentication module 48 may then check to determine whether theuser's account is current. Other authentication procedures mayalternatively be used. After it is determined that a call is valid, theauthentication module 48 will allow the call to proceed. Typically, abase station (e.g., base station 12 of FIG. 1) will first detect anoutgoing or incoming call for a particular user device. The base stationmay then contact the authentication module 48 within the server 42 toauthenticate the call. The authentication module 48 may then instructthe base station to either drop the call or allow the call to gothrough.

[0018] The network billing manager 50 is operative for tracking thefinancial accounts of individual users within the communication system.Often, a mobile user will be charged for both incoming and outgoingscalls. Thus, after the authentication module 48 has determined that aparticular call is authentic, the network billing manager 50 may recordcorresponding call information (e.g., user, duration of call, telephonenumber of other party, etc.) for billing purposes. The recordedinformation may later be used to prepare a monthly bill for the userbased on the user's agreement with the service provider. As shown inFIG. 3, a dedicated storage space 56 may be provided within the memory46 for the storage of billing information for each user in the system(or in a portion of the system).

[0019] The call log manager 52 is operative for maintaining a call logfor individual users at a network storage location. The call logmaintained for a user by the call log manager 52 will typically includethe same or similar information to that stored within a correspondinguser device within the system (e.g., within call log database 36 of FIG.2). That is, the call log may include call-related information for apredetermined number of previous calls associated with the user. Thecall log may include information relating to telephone calls placed froma user device associated with the user and/or telephone calls receivedby the user device associated with the user. A call log may bemaintained by the call log manager 52 for all users in the system or forselected users. In one approach, a dedicated storage space 58 isprovided within the memory 46 for each user for whom a call log is to bemaintained. The call log manager 52 may work independently or inconjunction with the network billing manager 50 to assemble the call loginformation for individual users. Alternatively, the call log manager 52may simply transfer the appropriate information to the call log of auser from corresponding billing entries in memory 46. As will beappreciated, other methods for assembling and maintaining the call loginformation may alternatively be used.

[0020] In one embodiment, the call log manager 52 only maintains calllogs for users who subscribe to a call log service (e.g., for a smallmonthly fee). When a user initially subscribes to the call log service,a certain amount of memory space may be allocated to the user within thenetwork (e.g., within memory 46) for use in storing the call log. Whenan authenticated call involving the subscribing user is later detected,the call log manager 52 may record the corresponding call information tothe dedicated call log memory space of the user. The call log manager 52may have to delete a call record from the memory space to make room forthe new call information. In one approach, the operation of the call logmanager 52 in maintaining a call log is automatic and transparent to thecorresponding user.

[0021] The address book manager 54 is operative for managing the storageof user-specific contact information for individual users at a networkstorage location. The user-specific contact information is informationthat is transferred to the address book manager 54 from a user deviceassociated with the corresponding user. In one approach, as illustratedin FIG. 3, a dedicated storage space 60 is provided at a networklocation for each user for whom contact information is to be maintained.Contact information may be maintained by the address book manager 54 forall users in the system or for selected users. In one implementation,contact information is only maintained for users who subscribe to anaddress book autosync service (e.g., for a small monthly fee). When auser subscribes to the address book autosync service, a certain amountof storage space may be allocated to the user within the network (e.g.,within the memory 46). The address book manager 54 may thereafter managethe transfer and maintenance of contact information to this storagespace for the user.

[0022] Transfers of contact information from a user device to the server42 may be initiated at either the user device or the network. In oneapproach, as described previously, a user device is programmed toinitiate transfers of contact information to the network atpredetermined times. When a transfer is to be made, the user device mayfirst place a call to the server 42 requesting storage of contactinformation at the corresponding network storage location. After thecall has been authenticated, the address book manager 54 may takecontrol of the transfer and storage of contact information to theappropriate storage location. In another embodiment, the address bookmanager 54 initiates the transfer of contact information from a userdevice to the network storage location by placing a call to the userdevice. Other methods for managing the transfer of user-specific contactinformation from a user device to the network may alternatively be used.

[0023] The memory 46 may include a single memory device or multiplememory devices. Also, any number of different memory types can be used.Preferably, non-volatile forms of memory will be used to prevent a lossof information should power be lost. As illustrated in FIG. 3, aseparate region of the memory 46 (or a separate memory devicealtogether) may be used for billing information (region 62), call loginformation (region 64), and contact information (region 66).Alternatively, all information associated with a particular user may bekept together within the memory 46. As will be appreciated, a widevariety of different techniques for organizing and storing theinformation within a network-based memory structure (or structures) maybe used.

[0024] In the embodiment of FIG. 3, the network billing manager 50, thecall log manager 52, and the address book manager 54 are all locatedwithin a common server 42. It should be appreciated that these functionsmay alternatively be distributed among multiple network servers in acommunication system. It should also be appreciated that these functionsmay each be implemented in a system without one or more of the otherfunctions.

[0025] When a user purchases a new user device, the call log and/orcontact information stored at the network storage location(s) associatedwith the user may be conveniently downloaded to the new user deviceduring an initial programming of the device. For example, in a cellularcommunication system, a vendor will usually program a new cellulartelephone for a purchaser to, among other things, associate anidentification number of the telephone with a telephone number assignedto the user. This process will typically require communication with aremote network server. During this programming operation, the vendor canperform a transfer of call log information and/or contact informationfrom the corresponding network storage location(s) to the new telephonefor the user. A nominal fee may be charged for the transfer(s). In oneapproach, for example, the vendor may deliver an appropriate request tothe call log manager 52 and/or the address book manager 54 to transfer aparticular user's information to the new user device. A specificauthorization or identification code (or the like) may be required toinitiate such transfers. The call log manager 52 and/or address bookmanager 54 may then retrieve the appropriate information and deliver itto the user device location.

[0026] User-initiated transfers of information from the network to auser device may also (or alternatively) be supported. For example, auser may deliver an appropriate request to the call log manager 52and/or the address book manager 54 to transfer the user's information tothe new user device. This may also require a specific authorization oridentification code (that the user can get from, for example, thecommunication service provider).

[0027] Because the contact information had been previously stored at anetwork storage location, the user does not have to recall and manuallyreenter the information in the new user device. Similarly, because thecall log information was stored at the server location, the new userdevice will have a record of previous calls that it would not otherwisehave. The ease and convenience associated with the transfer of the calllog and/or contact information to the new user device may encourage morefrequent user device upgrades and may also encourage consumer loyalty tothe service provider that is storing the information.

[0028]FIG. 4 is a flowchart illustrating a method 70 for processingcalls within a communication system in accordance with an embodiment ofthe present invention. First, a call is placed to or from a wirelessuser (block 72). A user authentication process is next performed todetermine if the user is valid (block 74). If the user is not valid, thesystem terminates the call (block 76 and block 78). If the user isvalid, the call is permitted to proceed (block 76 and block 80).Information about the call is subsequently added to a user billingdatabase for eventual use in billing the user (block 82). If the usersubscribes to a call log service, call information is also stored withina user-specific call log at a network storage location (block 84).

[0029]FIG. 5 is a flowchart illustrating a method 90 for performingaddress book auto-synchronization for a mobile user device in acommunication system in accordance with an embodiment of the presentinvention. A user first subscribes to an address book autosync serviceoffered by a communications service provider (block 92). The user thenactivates and initiates an address book autosync function on thewireless user device (block 94). During this time, the user may specifyan autosync timing criterion for use by the user device (e.g., everyMonday at 10:00 PM, etc.). The user device subsequently monitors aninternal clock for the appropriate autosync time (block 96). When theautosync timing criterion has been met, the user device automaticallycalls a remote server in the communication system to request transferand storage of user contact information to a network-based storagelocation (block 98).

[0030]FIG. 6 is a flowchart illustrating a method 100 for use inproviding an address book storage and retrieval service within acommunication system in accordance with an embodiment of the presentinvention. The method may be used in connection with automatic and/ornon-automatic information transfers initiated from a user device. A callis first received from a user device requesting storage of user-specificcontact information to a network-based storage location (block 102). Itis then determined whether a user associated with the user devicesubscribes to an address book service (block 104). This determinationmay be made, for example, during a user authentication process. If theuser does not subscribe to the address book service, the call isterminated (block 106 and block 108). If the user does subscribe to theservice, information relating to the call is added to a user billingdatabase (block 106 and block 110). Contact information is thentransferred from the user device to a dedicated network-based storagelocation associated with the user (block 112).

[0031] Although the present invention has been described in conjunctionwith certain embodiments, it is to be understood that modifications andvariations may be resorted to without departing from the spirit andscope of the invention as those skilled in the art readily understand.For example, forms of user-specific information other than contactinformation and call log information may also be used in accordance withthe present invention. Such modifications and variations are consideredto be within the purview and scope of the invention and the appendedclaims.

What is claimed is:
 1. A communication system for providingcommunication services to mobile users, comprising: a network billingmanager to maintain call information associated with a first mobile userat a first network storage location for use in billing the first mobileuser; and a call log manager to maintain call log information for thefirst mobile user at a second network storage location, said call logmanager to transfer said call log information to a user deviceassociated with the first mobile user in response to an appropriatecommand.
 2. The communication system of claim 1, wherein: said call loginformation includes information relating to a predetermined number ofprevious calls associated with the first mobile user.
 3. Thecommunication system of claim 1, wherein: said call log managerretrieves information from said first network storage location to bestored in said second network storage location as call log information.4. The communication system of claim 1, wherein: said second networkstorage location is located within a memory associated with a networkserver.
 5. The communication system of claim 1, wherein: said firstnetwork storage location and said second network storage location arewithin a common memory.
 6. The communication system of claim 1, wherein:said first network storage location and said second network storagelocation are within different memories.
 7. The communication system ofclaim 1, wherein: said network billing manager and said call log managerare implemented within a common network server.
 8. The communicationsystem of claim 1, wherein: said network billing manager maintains callinformation for multiple different mobile users and said call logmanager maintains call log information for multiple different mobileusers.
 9. The communication system of claim 8, wherein: said call logmanager maintains call log information for mobile users that subscribeto a call log service.
 10. The communication system of claim 1, furthercomprising: an address book manager to facilitate transfer and storageof contact information from a user device associated with a mobile userto a third network storage location.
 11. A mobile telephone for use in acommunication system, comprising: a data storage medium to store contactinformation for a user associated with the mobile telephone; and aninformation transfer module to automatically transfer contactinformation from said data storage medium to a network storage locationin the communication system at one or more predetermined times.
 12. Themobile telephone of claim 11, wherein: said information transfer modulecan be activated and deactivated by the user.
 13. The mobile telephoneof claim 11, wherein: said one or more predetermined times are userprogrammable.
 14. The mobile telephone of claim 11, wherein: said remotenetwork storage location is within a memory associated with a networkserver.
 15. A method for providing a service in a cellular communicationsystem, comprising: maintaining user-specific information at a networkstorage location in the cellular communication system for a user; andtransferring said user-specific information from the network storagelocation to a user device associated with the user when an appropriaterequest is received.
 16. The method of claim 15, wherein: saiduser-specific information includes user call log information.
 17. Themethod of claim 15, wherein: said user-specific information includescontact information associated with the user.
 18. The method of claim15, comprising: charging said user an extra fee for transferring saiduser-specific information.
 19. The method of claim 15, comprising:charging said user an extra fee for maintaining said user-specificinformation.
 20. A method for providing a service in a cellularcommunication system, comprising: providing storage of contactinformation for a user at a network storage location in the cellularcommunication system; and transferring contact information from thenetwork storage location to a user device associated with the user whenan appropriate request is received.
 21. The method of claim 20,comprising: maintaining a dedicated network storage space within thecellular communication system in which to store said contact informationfor the user.
 22. The method of claim 20, wherein: providing storageincludes facilitating transfer of contact information from a user deviceassociated with the user to the network storage location.
 23. A methodfor providing a service in a cellular communication system, comprising:maintaining a call log for a user at a network storage location in thecellular communication system; and transferring call log informationfrom the network storage location to a user device associated with theuser when an appropriate request is received.
 24. The method of claim23, comprising: maintaining a dedicated network storage space within thecellular communication system in which to store said call log for theuser.
 25. The method of claim 23, wherein: maintaining a call logincludes retrieving information from billing entries associated withsaid user for use in updating said call log.
 26. A method for supportinga call log service within a communication system supporting mobileusers, comprising: sensing a call in the communication system;determining whether the call is valid; and when the call is determinedto be valid: adding call information to a billing database for a mobileuser associated with the call; and when the mobile user associated withthe call subscribes to a call log service, updating a call logassociated with the mobile user that is stored at a network storagelocation.
 27. The method of claim 26, wherein: determining whether thecall is valid includes determining whether the call is associated withan authorized user in the communication system.
 28. The method of claim26, further comprising: transferring call log information from thenetwork storage location to a user device associated with the mobileuser when an appropriate command is received.
 29. The method of claim26, wherein: said network storage location is within a memory associatedwith a network server in the communication system.
 30. A method forsupporting an address book storage and retrieval service within acommunication system that services mobile users, comprising: receiving acall from a user device requesting storage, at a network storagelocation, of user-specific contact information; determining whether auser associated with the user device is a subscriber to an address bookservice; and facilitating transfer of user-specific contact informationfrom the user device to a network storage location when it is determinedthat the user is a subscriber to the address book service.
 31. Themethod of claim 30, wherein: determining whether the user subscribes tothe address book service is performed as part of a call authenticationprocess.
 32. The method of claim 30, comprising: transferring contactinformation from the network storage location to another mobile userdevice associated with the user when an appropriate request is received.33. The method of claim 32, wherein: said appropriate request isreceived from said another mobile user device during an initialprogramming of said another mobile user device by a vendor.
 34. A methodfor configuring a cellular telephone for a user for use within acellular communication system, comprising: assigning a telephone numberto the cellular telephone; associating the telephone number with anidentification number of the cellular telephone; and downloadinguser-specific information associated with the user from a remote networkstorage location in the cellular communication system and storing theuser-specific information within the cellular telephone.
 35. The methodof claim 34, wherein: the user-specific information includes user calllog information.
 36. The method of claim 34, wherein: the user-specificinformation includes contact information associated with the user. 37.The method of claim 34, comprising: charging said user a fee fordownloading said user-specific information.